Use nullptr/NULL instead of 0 for pointers, two fixes for undefined behavior #4996
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit fixes most
-Wzero-as-null-pointer-constant
warnings, except in some places which appear to be vendored 3rd party libraries, e.g. insdl_ttf.c
, libchdr, physfs and gmock and in 3rd party components therein. Since it might make more sense to update this 3rd party code to some later versions instead of fixing the warnings manually, I decided not to enable the C++ compiler flag inconfigure.ac
at this point.In two functions with the return type of std::string executed
return 0;
statements, causingstd::string
to be constructed from a null pointer. To avoid undefined behavior these were changed toreturn {};
.